home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX 6.2 Applications 1996 May
/
SGI IRIX 6.2 Applications 1996 May.iso
/
relnotes
/
Impressario
/
ch5.z
/
ch5
Wrap
Text File
|
1996-05-06
|
17KB
|
463 lines
- 1 -
5. _K_n_o_w_n__P_r_o_b_l_e_m_s__a_n_d__W_o_r_k_a_r_o_u_n_d_s
5.1 _I_m_p_r_e_s_s_a_r_i_o__P_r_o_d_u_c_t__S_p_e_c_i_f_i_c
+o The PostScript interpreter (psrip) when invoked runs
with the user ID of "lp" (suid lp). The PostScript
language includes file operators to read, write and
delete files. It is possible to write a PostScript
program to manipulate files and then submit it to psrip
to be run. The PostScript program running under psrip
would be able to read, write or delete any file that
can be accessed as user "lp".
+o If you install a printer driver that requires the
PostScript interpreter and a valid FLEXlm node-lock
license is not available for the PostScript
interpreter, the printer will still appear as a valid
choice from the Printer Manager. That is, the Printer
Manager does not warn you that you are installing a
printer that will not work until a valid FLEXlm node-
lock license is installed. Note that starting with
Impressario 2.0 printer drivers (all HP and Epson
drivers) that require the PostScript interpreter do NOT
install by default.
+o If you install Impressario 2.0 and have not removed and
replaced the printer (you must remove and replace the
printer using the printer manager anytime you upgrade
Impressario) print jobs may appear to fail silently if
a valid FLEXlm license is not available (an error will
be logged in /var/spool/lp/log indicating a license
failure but no other notification will be done).
Impressario 2.0 print drivers check for a valid license
and will print a message if a license failed. Older
drivers do not perform this check and do not print the
warning.
+o As part of the IRIX 6.2 upgrade process older
Impressario 1.2 images may be removed (depending on how
conflicts are resolved during the 6.2 installation).
This causes the history of installed Impressario sub-
systems to be "reset" and when you install Impressario
2.0 it may not install of of the same product images
that were previously installed under Impressario 1.2.
If this happens you may find that when you run the
Printer Manager to remove and re-install the printer
(part of the Impressario 2.0 update process) the
printer driver you require is not listed. If this
happens, it is likely that the impressario images for
impr_rip and impr_rip_printers have not been installed.
Installing impressario images for impr_rip and
- 2 -
impr_rip_printers (which are not installed by default
in Impressario 2.0)
will resolve this problem.
+o When running the script /usr/sbin/mkjtpr or
/usr/sbin/mknetpr to add a printer connected directly
to a network (with a network card or network adaptor)
the error message:
Could not ping network printer: <printer> Check network
connection to printer.
Continue anyway using <printer> as remote printer
name(y/n)[y]?
may be seen even though the printer is connected to the
network and can be pinged from a shell. This can
happen if the printer is on a different subnet. The
workaround is to ignore the error message and answer
"y" to the "Continue anyway..." prompt.
+o If you see messages in /var/spool/lp/log similar to:
UX:disable: WARNING: printer 'laserjet' now disabled
or the command "lpstat -t" returns a message similar
to:
/usr/lib/print/laserjet is not an executable. Please
reinstall...
it means that impr_rip and impr_rip_printers sub-
systems have not been installed and you have not
removed and re-installed the printer (using the Printer
Manager) since updating to Impressario 2.0 (part of the
Impressario 2.0 update process). This is the same
problem described in the previous bullet item except
you have tried to print before removing and re-
installing the printer and the lp spooler detected a
missing driver normally found in impr_rip_printers and
shut down the queue for this particular printer.
+o Some scanners may require that a modification be made
to the /var/sysgen/master.d/wd93 file before the
scanner will work under IRIX 6.2. The Ricoh FS1
scanner will require this. Other scanners may continue
to work without the change but you might see a SCSI bus
timeout when you first add the scanner using the
scanner manager (adding the scanner a second time with
the scanner manager then works). If you see these
symptoms change the wd93_syncenable value in
- 3 -
/var/sysgen/master.d/wd93. Instructions for changing
the array elements are in the /var/sysgen/master.d/wd93
file. By default, the array values are all set to
0xfe. If the current value is 0xfe you can use this
chart to determine the value to use:
SCSI ID of scanner wd93_syncenable value to use
2 fa
3 f6
4 ee
5 de
6 be
7 7e
If the current value is not 0xfe then do not use the
above chart and make sure you understand the
instructions in the /var/sysgen/master.d/wd93 file
before making any changes. You can determine the SCSI
ID of the scanner by looking at the back of the scanner
near the SCSI cable or by typing the hinv(1M) command.
The hinv(1M) command will also tell you which SCSI
controller the scanner is connected to (for most
systems it will be SCSI Controller 0). Note that some
scanners identify themselves as a CPU device and
hinv(1M) will report them as a CPU in this case.
After updating /var/sysgen/master.d/wd93 build a new
kernel with the command "/etc/autoconfig -f" and then
reboot the system.
+o The Ricoh FS1 and Sharp scanners will not work with the
optional GIO SCSI card for Indy systems (use the
built-in SCSI port, instead).
+o The filter /usr/lib/print/text2pcl sends a debug
message to standard out similar to "text2pcl: st-
>vertical_addr= 3150, 100" when run. When printing,
the spooler will record this message in
/var/spool/lp/log. This message can be ignored.
+o HPGL/2 Files: Impressario cannot automatically
recognize HPGL/2 files. To print HPGL/2 on your
DesignJet plotter, you must select the "None (pass file
"as is")" from the graphical options panel, or by
inserting the word "raw" into the saved options in the
printpanel "Printer Specific Options" area. Otherwise
HPGL/2 files may be incorrectly auto-recognized as text
files, and printed literally. Please note that when
you select "None (pass file "as is")" you cannot print
other file types: data is sent unprocessed to the
printer. Install a second network queue for the
- 4 -
printer and save different options for each queue if
you wish to have both interfaces available
simultaneously: see the _I_m_p_r_e_s_s_a_r_i_o _U_s_e_r'_s _G_u_i_d_e for
more information on doing this.
+o If you run out of disk space in /_u_s_r/_t_m_p on the
Impressario server, print jobs fail silently.
+o Hewlett-Packard LaserJet II and III series printers do
not work properly with less than 1.5 Mbytes of memory.
LaserJet 4 series printers require at least 4 Mbytes of
memory. If your output is garbled or only partially
printed, make sure that you have enough memory
installed in the printer.
+o If you cancel a plot job on a DesignJet plotter using
the plotter's front panel CANCEL button the SGI print
spooler will not realize that the plot has been
canceled. You should first cancel the job using the
cancel(1) command or from the PrintStatus panel and
then press the cancel button on the plotter.
+o Support for the Apple LaserWriter covers the
LaserWriter Plus, II, IINT, IINTX, IIf, and IIg. Any
other models of Apple LaserWriter are not currently
supported.
+o Apple LaserWriter IIf printers with less than 4 Mbytes
of memory are not supported.
+o Apple LaserWriter IIg printers with less than 8 Mbytes
of memory cannot print the entire imageable area of the
page. You must send the file
/_u_s_r/_l_i_b/_p_r_i_n_t/_d_a_t_a/_L_W__2_G__p_h_o_t_o_g_r_a_d_e__o_f_f to printers
with less than 8 Mbytes of memory using the command:
ccccaaaatttt ////uuuussssrrrr////lllliiiibbbb////pppprrrriiiinnnntttt////ddddaaaattttaaaa////LLLLWWWW____2222GGGG____pppphhhhoooottttooooggggrrrraaaaddddeeee____ooooffffffff >>>> ////ddddeeeevvvv////ttttttttyyyydddd[[[[nnnn]]]]
where [_n] is the serial port number. This file turns
off the PhotoGrade feature of the printer. The
recommended solution is to upgrade your printer to at
least 8 Mbytes of memory.
+o You may experience SCSI resets when attempting to open
the Sharp JX-320 scanner.
+o For manual feed to work on an HP 4MPlus LaserJet
printer MP tray must be set to FIRST from the front
panel.
- 5 -
+o If you have problems with image clipping while printing
a B size image with an HP 4V LaserJet printer you
should set resource save to off from the printer front
panel (go into the MEM CONFIG MENU and set
RESRCSAVE=OFF). Optionally, you can add more memory or
reduce the resolution.
+o If you can not print pdf files you should run
acroread(1) from the command line (on the print server)
and accept the license terms and conditions.
+o HP LaserJet 4P owners must set the paper size on the
front panel and make sure it is the same paper size
specified using the Impressario Options panel. A
mismatch between the front panel setting and the paper
size specified in a PCL job can cause a paper jam with
this printer (this is a limitation of the printer).
+o The file /usr/lib/filetype/install/Image.ftr can cause
Jpeg files to not be printed if it exists. This file
should be removed (or moved to another directory).
After removing, cd to /usr/lib/filetype and type "make
clobber" then "make" as root to rebuild the filetype
rules. Jpeg files should then print.
(/usr/lib/filetype/install/Image.ftr was distributed
with some IRIX 5.3 software bundles and is not needed
in IRIX 6.2).
+o If you see messages like:
%%[ Error: invalidfont; OffendingCommand: findfont ]%%
%%[ Flushing: rest of job (to end-of-file) will be
ignored ]%% Helvetica not found, using Courier. %%[
Error: invalidfont; OffendingCommand: findfont ]%% %%[
Flushing: rest of job (to end-of-file) will be ignored
]%% laserjetPJL: ERROR: No data read from input stream!
laserjetPJL: Not a valid tiff stream %%[ Error:
invalidfont; OffendingCommand: findfont ]%% %%[
Flushing: rest of job (to end-of-file) will be ignored
]%%
it means dps_eoe and/or x_eoe.sw.xdps have not been
installed. The directory /usr/lib/DPS is probably
missing AdobeFonts.upr which is built after
dps_eoe.sw.dps is installed (an exitop from
dps_eoe.sw.dps using the makepsres(1) command builds
AdobeFonts.upr).
+o If your fonts do not appear correct in the printed
output or fonts of one type are being substituted for
another type you may not have all of the available
- 6 -
fonts loaded on the print server. Verify the subsystem
x_eoe.sw.Xfonts is loaded with the command "versions
-av x_eoe.sw.Xfonts". If nothing is listed from the
versions command then it is not installed. If it is
not installed, you can install it from your IRIX 6.2
CD. Note that x_eoe.sw.Xfonts is not loaded by default
on server systems (any system that does not have a
graphics head).
+o If you get these errors in ~lp/log for a serial
printer:
laserwriter: Error querying device attributes. Reason:
Invalid argument. UX:cat: ERROR: Write error (0/4096
characters written): Broken pipe
check to see if another process is running on the port
by typing:
ps -ef|grep tty
The midi process running on the same port as a printer
can cause this problem.
+o The level II PostScript interpreter used in Impressario
2.0 uses Color Rendering Dictionaries (CRDs) to color
correct PostScript files that specify color in CIE
color space. PostScript files that do not use the CIE
color space can not be color corrected (an example are
PostScript files generated by ShowCase and Netscape).
A rudimentary color correction can be achieved by
converting these PostScript files to tiff images and
then print the tiff image using psrip. To do this, use
this command:
showcase -p showcase_file | /usr/lib/print/psrip -B8
-Crgb | lp
or
cat file.ps | /usr/lib/print/psrip -B8 -Crgb | lp
where file.ps is an existing PostScript file. Note
that psrip is the software licensed Adobe PostScript
interpreter and it is likely that psrip will only run
on the print server.
+o If you run gscan on a dual head (XL-XL) 8-24 bit
graphics system gscan will not redraw the red box it
uses to outline the scan area if the gscan window is
moved. gclear can be used to remove the red box in
- 7 -
this case.
5.2 _T_h_i_r_d__P_a_r_t_y__P_r_o_d_u_c_t_s
By design, IRIX 6.2 will not run COFF binaries so any
Impressario driver that uses COFF binaries will not run
on IRIX 6.2/Impressario 2.0.
+o SeikoPrint for Impressario 1.1 contains COFF binaries
and will not run under IRIX 6.2/Impressario 2.0.
+o Tektronix PhaserPrint for Impressario 1.0 contains COFF
binaries and also uses the obsoleted chunky data format
(see next item). As of this writing Tektronix has said
they will not be supporting Impressario 2.0. If you
are using PhaserPrint for Impressario 1.0 you should
not update the system to IRIX 6.2 / Impressario 2.0.
+o Genicom GenicomPrint 1.1 for Impressario 1.1 and
GenicomPrint 1.2 for Impressario 1.1 from Genicom
contain COFF binaries and will not run on IRIX
6.2/Impressario 2.0.